home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
ava40.zip
/
AVACFG.DOC
< prev
next >
Wrap
Text File
|
1991-02-14
|
15KB
|
514 lines
** # # ### ## # # ## ### ### ###
* * # # # # # ## ## # # # # # #
**** # # # # # # # # # #### # ## # #
* * ## # ## # # # # # # ### ###
* * ### ### ### ### ### ### ## ### ### ## # #
* * # # # # # # # # # # # # # ## #
* * ## ### # ## # # #### # # # # # ##
* ### # # ### # ### ### # # # ### ## # #
** # ## ## ### ### ### # # # #
* * # # # # # # # # # # ## ##
**** # # ## # # ### # # #### # # # #
* * ### ## ## # # ### # # # # # #
Configuration utility for AVA and AVA SF
This program is supported by:
Cat Miller
The Alternate Choice
(602) 951-8534
1:114/39
Documentation by Cat Miller and Geoffrey Booher
PREFACE
-------
Disclaimer
----------
AVACFG is provided as is, without warranty of any kind, either expressed
or implied. In no way, shall Cat Miller be held liable for any damages
by use or misuse of the forementioned program. Your use of this program
implies your acceptance of these terms. You will bear total
responsibility.
Introduction
------------
This configuration utility serves two purposes. It will create the
necessary configuration file used by AVA and register your copy of AVA.
Register.Ava and enter the registration number sent to you.
AVACFG was written using QuickBasic 4.5. It is necessary to have the
external run time library BRUN45.EXE somewhere in your DOS path.
Using AvaCfg
------------
AVACFG uses an optional command line parameter. The command line
parameter is the path to your AVA directory. If no path is specified
AVACFG will default to the current directory. If Ava.Exe is not found in
the path specified or in the current directory, AVACFG will return to DOS.
If this is a first time installation Avacfg.Exe will use a default set
of parameters. You can edit the default settings to your suit your
particular needs.
Use your cursor keys to move the cursor to the menu option and press
[Enter] to select that option. The [Esc] key will back out and abort any
function.
When editing, the Up/Down cursor keys will move you from field to field.
To change a field just type in the new value. Press [Enter] or move out
of that field with your Up/Down cursor keys when you are done. The toggle
fields will be so marked. Pressing any key in these fields will toggle
the value. Press [Enter] or move out of that field with your Up/Down
cursor keys when you are done.
Configuration file entries
--------------------------
1> BBS Name
--------
Enter your BBS name here.
2> LD or Toll calling
------------------
Toggle yes to this question if you want to call long distance or toll phone
numbers. If you plan to support calling Long Distance or Toll phone
numbers for verification only, then you must toggle Yes to this field.
A toll call is defined as a call within your areacode with which an
additional rate is charged.
3> Grant minimum access
--------------------
If you answered No to field #2 then you might want to consider granting
a minimum access level to callers who meet this criteria. Granting minimum
access will give the caller the chance to look around your board until you
get around to upgrading their status.
A No in this field will disable this feature and the caller will not be
able to use AVA.
4> Verified security level
-----------------------
Enter the security level granted to callers who pass verification. Be sure
that this security level is defined in Limits.Ctl.
Configuration File Entries
--------------------------
5> Verified download byte limit
----------------------------
Enter the daily download byte limit associated with field #4. Download
bytes are counted in kilobytes. NOTE: Not supported by SpitFire
6> Verified daily time limit
-------------------------
Enter the daily time limit associated with this level.
7> Minimum access security level
-----------------------------
This is the access level granted to callers if you answered Yes to option #3.
Be sure that this level is defined in your Limits.Ctl file for QuickBBS,
RemoteAccess or SuperBBS systems.
8> Minimum access download byte count
----------------------------------
Enter the daily download byte limit allowed. Be sure that this matches
that which is defined in your Limits.Ctl file. NOTE: Not supported for
SpitFire.
9> Minimum access daily time limit
-------------------------------
Enter the daily time limit, in minutes, allowed for this level. Be sure
that this matches that which is defined in your Limits.Ctl file.
Configuration File Entries
--------------------------
10> Area Code
---------
Enter your area code here. This is used to check against phone numbers
entered by callers. It also plays a part in reformatting RemoteAccess
free-style phone number format. If you wish not to use PhoneNum.Ava to
check for valid numbers, your area code is an important part in determining
the kind of calls AVA will or will not place.
11> Edit phone number
-----------------
Normally you wouldn't use this but, toggle Yes if you want to support this
feature. Numbers are always checked against AVA's data file and checked
for invalid characters and invalid digit sequences. Preferably, you would
answer No to this feature. However, after a caller edits his number it is
written to AVA.Log along with the original number.
12> Allow duplicate phone numbers
-----------------------------
Toggle Yes if you would like to support this feature. Answer No if you do
not.
13> SysOp Security Level
--------------------
This is here so that you can test AVA from the local console or remote. If
you want to determine which configuration best suits your needs then this is
a good way to find out.
Configuration File Entries
--------------------------
14> LD calls for verification only
------------------------------
A No will disable this feature while a Yes input will enable this feature.
With this feature enabled, AVA will call long distance numbers. Once the
caller is verified, AVA will terminate the connection after informing the
caller of their verified status and to call back at their convenience.
15> Toll calls for verification only
--------------------------------
A No will disable this feature while a Yes input will enable this feature.
With this feature enabled, AVA will call toll numbers. Once the caller is
verified, AVA will terminate the connection after informing the caller of
their verified status and to call back at their convenience.
16> Long Distance or Toll calling time
----------------------------------
If you do not wish to support calling Long Distance or Toll numbers during
a specific time period, then enter 00:00 00:00 to the 'Enter STARTING and
ENDING ...' question. This will disable that function.
17> Modem initialization string
---------------------------
Enter an ATS0=0 to turn off auto answer. Since your modem is already
initialized, there is no reason to initialize it again. Pressing enter and
leaving this field blank, AVACFG will use the default ATS0=0X4.
NOTE: For the newer HST/V.32bis modems - you will want ATB1 in your
initialization string somewhere. This is needed for a faster connect.
Recommended HST/V.32bis/V.42bis entry: ATB1E0Q0V1X6
Configuration File Entries
--------------------------
18> Baud rate to open comport
-------------------------
Enter a 0 here if you want to initialize the comport to the caller's baud
rate. Otherwise toggle the baud rate you wish to use.
If you use a U.S. Robotics Courier HST modem, and are locking the port at
19200 or 38400 - toggle the baud rate to the locked speed of your FOSSIL
or serial port.
19> Seconds to wait for connect
---------------------------
Enter the seconds you want AVA to wait for a carrier from the remote site.
The default is 30 seconds.
20> Handshake
---------
This is the hardware handshake used between your computer and modem. The
acceptable inputs are:
0 = No handshake
1 = XON/XOFF
2 = CTS
3 = BOTH XON/XOFF and CTS
The default is 0.
If you have a high-speed modem such as a U.S. Robotics Courier HST, and you
are locking the serial port/FOSSIL driver at 19200 or 38400, and are using
RTS/CTS flow control (&B1&H1&R2) be sure to use handshake option 2 - CTS.
Configuration File Entries
--------------------------
21> Dial prefix
-----------
You can now define your dialing prefix. You will have a choice between
ATDT or ATDP. The default is ATDT.
22> Verification ONLY
-----------------
This feature works similiarly to the LD or TOLL verify only option but this
option applies to LOCAL calls. This is for the SysOps who run their BBS'
on measured telephone lines.
23> Minimum minutes
---------------
This feature allows you to define the minimum amount of time necessary for
AVA to perform the verification. You can disable this feature by using a
0.
24> Use Phonenum.Ava
----------------
Toggle Yes to this option if you want AVA to check for valid calling
numbers in Phonenum.Ava. If you answer No, AVA will use it's internal
checking as before. Please refer to option #25.
25> Grant minimum access if number not found in Phonenum.Ava
--------------------------------------------------------
Toggle Yes to this option if you wish to grant minimum access to callers
whose numbers are not found Phonenum.Ava. Please refer to option #24.
Configuration File Entries
--------------------------
This section does not pertain to SpitFire systems.
FLAG A, B, C, D
---------------
AVA is also able to manipulate the FLAGS. You must remember that each
flag consists of 8 'slots' or bits. Each slot must be filled with
either an x or a - (hyphen). If you are going to NULL or not use a flag
then there must be 8 hyphens.
A blank or NULL flag looks like this:
A FLAG: --------
A FLAG with the first bit set will look like this:
A FLAG: X-------
AVACFG will NOT catch and correct blank slots. If you are using the
FLAGS then you are already aquainted with them so nuff said. However,
if you are not and don't intend to use them, just press enter to these
questions and AVACFG will default to a blank flag. This is valid only
for a new setup.
AVA now respects current flag settings and will not reset them. However,
if you have set a flag(s) specifically to allow access to AVA, then you
must set this same flag(s) in AVACFG. This is so AVA will reset this
flag(s) if verification was successful or the caller is granted minimum
access. On an unsuccessful verification, AVA will NOT rest this flag(s).
As an example, you have set Flag A to allow new callers to use AVA:
Flag A: X-------
You MUST set this same flag in AVACFG. Upon a successful verification AVA
will reset this flag. Your Flag A will then look this:
Flag A: --------
Verified callers will no longer be able to access AVA.
Configuration File Entries
--------------------------
30> Use Direct screen writes
------------------------
Toggle this option to allow direct screen writes. AVA defaults to No,
where it will use dos for screen writes.
Support
-------
Updates and or new releases of AVA can be downloaded or file requested
from the support board, The Alternate Choice, 114/39, (602)951-8534,
300/1200/2400. The magic filename is, AVA.
If you are installing AVA for the first time I will offer assistance.
You may leave your questions, comments and suggestions to Cat Miller if I
am not available for chat.
If you do send netmail, you can start polling for a reply within 48 hours.
Registered SysOps will have access to the OTW Support message base and
should leave their messages there. You may also contact one of the
following Support Systems for assistance.
* AVA Distribution/Support System *
SysOp: Geoffrey Booher
BBS: The Gateway Net BBS - a FrontDoor/RemoteAccess System
14.4 HST / 14.4 V.32bis / 9600 V.32 / V.42bis 20 hrs
FidoNet: 1:11/233
Number: (815)233-5008 Freeport, IL - USA
Comments: FREQ magicname: AVA for the latest version
AVA QuickBBS, RemoteAccess, SuperBBS support USA
* AVA SF Distribution/Support System *
SysOp: Russell Mikami
BBS: The Hawaiian Hawke BBS - A SpitFire System
9600 V.32 / 14.4 HST 24 hrs
FidoNet: 1:114/67
Number: (602)272-4887 Phoenix, AZ - USA
Comments: Netmail - SpitFire support
Gratitude
---------
Geoffrey Booher for his comments and suggestions for version 1.0 and
later.
To the many others who took the time to send me your critisisms,
suggestions and comments.
Thank you to the beta team, with whose help and support provides
for a good, clean running program.
My sincere gratitude to all who have registered!
Acknowledgements
----------------
QuickBasic 4.5 is a product of MicroSoft.
Courier HST is a product of U.S. Robotics, Inc.
RemoteAccess is a product of Continental Software.
QuickC com library used with AVA is written and developed by Jeff
Sumberg. He has developed an excellent library and can be found on
most BBS's as QBSERxx.Zip.
APPENDIX A
----------
AVACFG 4.0: Released with AVA v4.0. Feb. 1991
Previous versions are not compatible
AVACFG 3.7: Released February 1991.
Previous versions are not compatible
AVACFG 3.06
AVACFG 3.05: Released September 1990.
AVACFG 3.01: Released August 1990.
AVACFG 3.0ß: Released August 1990 with AVA v3.0ß.
Previous versions are not compatible
AVACFG 2.3: Released March 1990. Previous versions of AVACFG are not
compatible. Released with AVA 2.3.
AVACFG 2.0: Released December 1989. Previous versions of AVACFG are
incompatible. This is released with AVA 2.0.
AVACFG 1.1: has been upgraded to suit AVA11f. Support includes
defining your modem init string and baud rate to open the
comport. The latter should be set to your modem's highest
baud rate, irregardless of what the caller's baud rate is.
AVACFG 1.1: was distributed with AVA 1.1d BETA. Previous versions of
AVA are not compatible.
AVACFG 1.0: was distributed with AVA 1.1 BETA.
Initial release: May 1989